Explanation of Change

Fixed Issues

$ #84281
PROPOSAL:

Tests

• Same as QA Steps

• Verify that no errors appear in the JS console

Offline tests

1. Follow steps 1–3 from the QA Steps above to set up test data
2. Turn off network (airplane mode or disconnect Wi-Fi)
3. Select 2–3 cash expenses and click "Duplicate expense"
4. Confirm duplicated expenses appear optimistically in the list while offline
5. Turn the network back on
6. Confirm the duplicated expenses persist after syncing with the server
7. Confirm no duplicate or missing entries after reconnection

QA Steps

1. Log in to the app
2. Go to expense chat
3. Create several test expenses:
   • At least 2 cash expenses (submitted by you)
   • At least 1 Per Diem expense with start & end dates
   • At least 1 Per Diem expense without start or end dates (if possible)
   • At least 1 Distance expense
   • At least 1 card expense (company card)
   • At least 1 expense with a receipt currently scanning
   • At least 1 expense on a report where you are not the submitter (e.g., as an approver/manager)
4. Navigate to the Reports page → Expenses tab
5. Verify option visibility (cash expenses):
   • Select a single cash expense (yours) → open the bulk actions menu
   • Confirm "Duplicate expense" option appears
   • Deselect all
6. Verify option visibility (multiple cash expenses):
   • Select 2 or more cash expenses (yours) → open the bulk actions menu
   • Confirm "Duplicate expense" option appears
   • Deselect all
7. Verify card expense exclusion:
   • Select only a card expense → open the bulk actions menu
   • Confirm "Duplicate expense" does NOT appear
   • Deselect all
8. Verify mixed card + cash exclusion:
   • Select a cash expense AND a card expense together → open bulk actions menu
   • Confirm "Duplicate expense" does NOT appear
   • Deselect all
9. Verify scanning expense exclusion:
   • Select an expense that is currently scanning → open bulk actions menu
   • Confirm "Duplicate expense" does NOT appear
   • Deselect all
10. Verify mixed scanning + cash exclusion:
    • Select a cash expense AND a scanning expense together → open bulk actions menu
    • Confirm "Duplicate expense" does NOT appear
    • Deselect all
11. Verify Per Diem without dates exclusion:
    • Select a Per Diem expense that has no start or end dates → open bulk actions menu
    • Confirm "Duplicate expense" does NOT appear
    • Deselect all
12. Verify Per Diem with dates — allowed:
    • Select a Per Diem expense that has both start & end dates → open bulk actions menu
    • Confirm "Duplicate expense" DOES appear
    • Deselect all
13. Verify non-submitter exclusion:
    • Select an expense from a report where you are NOT the submitter (e.g., you are the approver) → open bulk actions menu
    • Confirm "Duplicate expense" does NOT appear
    • Deselect all
14. Verify mixed submitter + non-submitter exclusion:
    • Select one of your own expenses AND one from a report where you are not the submitter → open bulk actions menu
    • Confirm "Duplicate expense" does NOT appear
    • Deselect all
15. Verify expense report tab exclusion:
    • Switch to the Reports tab
    • Select one or more reports → open bulk actions menu
    • Confirm "Duplicate expense" does NOT appear
    • Switch back to Expenses tab
16. Verify distance expense — allowed:
    • Select a distance expense (yours) → open bulk actions menu
    • Confirm "Duplicate expense" DOES appear
    • Deselect all
17. Verify mixed allowed types:
    • Select a cash expense, a Per Diem (with dates), and a distance expense together → open bulk actions menu
    • Confirm "Duplicate expense" DOES appear
    • Deselect all
18. Verify bulk duplication works:
    • Select 2–3 cash expenses, note their amounts, merchants, and categories
    • Click "Duplicate expense"
    • Confirm the selection is cleared after clicking
    • Confirm new duplicated expenses appear in the list
    • Verify each duplicated expense has the correct amount, merchant, category, and currency
    • Verify the date on each duplicate is set to today
    • Verify receipt images are NOT copied to the duplicates
19. Verify duplication works for Draft expenses
20. Verify duplication works for Processing (submitted) expenses
21. Verify duplication works for Approved expenses
22. Verify duplication works for Paid/Reimbursed expenses
23. Verify single duplicate still works:
    • Open a single expense from its report
    • Use the three-dot menu → "Duplicate"
    • Confirm the expense is duplicated correctly with the same fields
    • Verify the single-duplicate animation (icon changes to checkmark, text to "Duplicated", then reverts)
24. Verify no regression on other bulk actions:
    • Confirm bulk Hold, Unhold, Delete, Approve, Pay actions still work as expected when selecting eligible expenses

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos